Testing and auto-generated ids in SproutCore

written by admin

martinottenwaelter:

> > If you’re trying to automate tests of your [SproutCore](http://sproutcore.com) application with [Selenium](http://seleniumhq.org/), for example, you’ll realise that the HTML element ids are automatically generated. They change every now and then and break all your tests. > > > > To get rid of this problem, you can override the `layerId` method of certain view classes to generate a stable, and human readable, id. > > > > The following code takes the view hierarchy, and generates an id based on the parents’ names. For example, the `mainPage.mainView.someOtherView.theTargetView` view will be given the `mmsome.theTargetView` id. > >

Tasks

written by admin

Link: Tasks

Tasks Screenshot

In case you haven’t been following the mailing list, Suvajit Gupta and some associates have been working on a really nifty software planning tool called Tasks.  They are using Tasks to plan some large software projects internal to their own company and they are also adding features we need to use Tasks to manage the SproutCore project as well.

Thanks to their hard work, we now have an alpha version of Tasks up and running with all of the SproutCore issues ported over from Lighthouse at tasks.sproutcore.com.

Please head on over and give it a try.  Then leave a comment here or get on the SproutCore mailing list and let us know what you think.

There are still a number of rough edges that need to be polished, but it sure is nice to finally have a really fast web-based bug tracking system.